Alert notification system

ABSTRACT

A system for providing alert notifications to multiple persons or to a plurality of related geographic locations. The system stores a database of information including a plurality of communications identifiers and additional information for subscribers having those identifiers, including geographic locations and/or school/organization membership information. The system responds to commands identifying alerts to be delivered to affected geographic areas or schools/organizations, by retrieving communications identifiers in the threatened geographic location or associated with the named school/organization, establishing a communications connection using each retrieved communication identifier, and delivering the alert. Alerts may be initiated by authorized personnel via telephone or Internet interaction with the system, or may be generated automatically from data feeds such as the EMWIN system of the National Weather Service. Alerts may be delivered via telephone, pager (voice or text), e-mail, Internet, or other media.

FIELD OF THE INVENTION

The present invention relates to the delivery of emergency informationto persons needing to be notified of such information.

BACKGROUND OF THE INVENTION

Populations are increasing throughout the United States and globally.Population concentration increases the impact of localized emergenciessuch as weather, chemical spills, floods, etc., and thus increases theimportance of notifying the public of emergency conditions in a timelymanner.

Emergency services and public safety organizations have establishedtechnological systems that help to identify and communicate emergencysituations. For example, emergencies may be centrally reported via 911telephone communication systems, and disseminated via radio, satelliteor Internet communications. Prediction methodologies have improved earlydetection of pending threats, particularly weather related threats suchas tornadoes and floods, and communications networks have expanded toassist in the dissemination of this information. According to theNational Weather Service (NWS) report “Reinventing Goals for 2000 StatusB March 1999”, the NWS requested $42.1 million in FY2000 for it'sNatural Disaster Reduction Initiative (NDRI 2000) to continue tomodernize and improve lead-times for severe weather events and expandthe number of NOAA Weather Radio (NWR) stations. Forecasting anddetection technologies, coupled with almost real-time distributionnetworks, have improved the average lead-time for severe weather eventsdramatically. Statistically, the NWS reports average lead-timedetections for thunderstorm events are currently 17.9 minutes. This isan improvement of 43% over the pre-modernization lead-time lead timesdetection of 12.5 minutes for thunderstorms. Likewise, the improvedtornado lead-time detection average is currently 11.0 minutes; improvedby 162% over the pre-modernization lead-time average of 4.2 minutes.Furthermore, flash flood detections currently stand at 52 minutes oflead-time with an astounding improvement of 491%. Substantial increasesin lead-time detection should contribute to more effective notificationand ultimately more lives saved.

Although these improvements have provided greater accuracy and lead timein severe weather notifications, such notifications do not seem to beadequately communicated to citizens. Preliminary data as of Jul. 13,1999 for the year 1999, shows that 99% of the total fatalities fortornadoes occurred during tornado watches. Statistics for 1998 similarlyshow 85% of all fatalities also occurred during tornado watches. Many ofthese fatalities could have been avoided if the persons involved hadsought adequate shelter. This clearly indicates that there is a weaknessin the existing infrastructure for notifying citizens of severe weatherconditions. A review of this infrastructure and its shortfalls is thusin order.

Currently, the National Weather Service (NWS) collects and disseminatesnear real-time weather data to help identify and distribute alerts,watches and weather warnings for specific geographical regionsaround-the-clock over various distribution networks. For the cost ofessential down link equipment, virtually anyone may receive nearly allthis information at no charge. However, identifying what information ispersonally relevant does require the continuous sorting and digestion ofthe entire data stream 24 hours a day and seven days per week.Practically speaking, many individuals just have no need for the entiredata stream. They just need to know when an emergency pertains to themspecifically, no matter where they are and no matter what time of day.For this, people rely on local media organizations and governmentorganizations to monitor and provide notification should an emergencyoccur. Many public and private entities currently receive this datastream, then parcel, process, categorize and sometimes enhance thisinformation to rebroadcast over various distribution networks so localcitizenry, populations and private industry may be alerted or informed.Nevertheless, the typical citizen must rely upon the vigilance of publicand private media broadcasters to constantly monitor this data streamand get “the word out” in time of emergency.

To help provide additional insurance and improve the likelihood fornotification, individuals can purchase a NOAA Weather Radio (NWR)receiver. NOAA Weather Radio (NWR) is a service of the National Oceanicand Atmospheric Administration (NOAA) of the U.S. Department ofCommerce. As the “Voice of the National Weather Service”, it providescontinuous broadcasts of the current weather information as well ashazardous local environmental conditions. Furthermore, a NWR receivercan detect codes in a NWR broadcast indicative of hazardous weatherconditions, and respond by producing a special alarm signal that isseparate from normal playback of weather broadcasts.

Most NOAA weather stations broadcast 24 hours a day, but NWR coverage islimited by nature and design to an area within 40 miles of thetransmitter. Those living in cities surrounded by large buildings andthose in mountain valleys with standard receivers get little or noreception at considerably less than 40 miles. As of February 1998,approximately 70 to 80 percent of the U.S. population are capable ofreceiving NOAA Weather Radio broadcasts. Most recently, as a result ofthe “Gore Initiative”, there has been 99 new NWR stations put intooperation and funding is being sought for 100 new stations to ultimatelyachieve a 95% population coverage in each state. Thus, ultimately thesystem will leave at least 5% of the population unable to hearbroadcasts or weather alerts.

Of course, the 95% coverage figure quoted in the previous paragraph,assumes that everyone within the coverage area of a NOAA Weather Radiotransmitter has purchased a NWR receiver and will always have it turnedon. Unfortunately, many people that actually own a NOAA Weather Radiooften leave it unattended and unmonitored. There are several reasons forthis, ranging from misuse of the equipment to discomfort with leavingany household appliance continuously on. Perhaps the most perniciousproblem is that weather broadcasts must cover a relatively large areaand so many of the alert signals transmitted by those broadcasts will beirrelevant to a large percentage of the listening population. Forexample, flood or tornado warnings are typically applicable only tolisteners in a subsection of a particular county, while the remaininglisteners are not in substantial danger. Unfortunately, however, allcitizens that are tuned to the weather broadcast will hear the alertsignal for every localized emergency. This results in the situation notunlike the fable of the Boy Who Cried Wolf, in which citizens decidethat the warnings are not normally relevant, and either ignore them orturn their NWS receiver off. Most particularly, citizens often do notplace a NWS receiver in their bedroom, because they would rather not bedisturbed at night unless there is a certain life-threatening emergency.This perhaps explains why tornadoes and floods that occur at night areoften the most deadly, because citizens do not-receive emergencynotifications.

Local municipalities have sometimes utilized civil defense siren systemsto sound loud audible alerts in time of emergency to help capture theattention of urban residents. However, the sounding of an emergencysiren can be confusing, requiring the notification recipient to seekadditional information. The siren could mean a severe weather emergency,a chemical spill, volcanic eruption, a monthly system test or any othercondition that local government decides to note (such as a “noonwhistle”). Many citizens will, as a consequence, ignore such sirensrather than invest the time to determine their meaning. Furthermore,under the best conditions, the effectiveness of a siren is dependentupon proximity to the siren. Citizens that live near to the siren, livein poorly sound-insulated buildings, have normal hearing and/or arelight sleepers, are much more likely to be notified of emergencies thancitizens that live far from the siren, live in quiet buildings, arehearing impaired and/or are sound sleepers. As a consequence, it hasbeen found that many people sleep right through nighttime siren alerts,and many severe weather fatalities are attributable to people just nothearing a siren. Further diminishing this system's effectiveness, manysiren systems are over 50 years old and plagued with maintenanceproblems. Furthermore, sirens evidence spotty urban population coveragedue to urban expansion that has outgrown system capacity.

Similar problems of notifying citizenry arise in non-weather relatedemergencies. For example, when there is a chemical spill or explosivethreat, appropriate emergency services are dispatched to attempt tomitigate the impact to human health or property. Often, the full scopeof the emergency can not be ascertained until emergency crews actuallyarrive at the scene. If the emergency has the potential to escalate andendanger more lives and other communities, emergency organizations mustagain rely on broadcasting for notification.

The United States Environmental Protection Agency (U.S. EPA) requirescompanies to develop Risk Management Program (RMP) plans. The requiredRMP plans describe chemical risks at industrial sites and the programsthese facilities use to prevent accidental releases and minimize theimpact on human health in the unlikely event that a release shouldoccur. When applicable, the RMP includes air dispersion modeling todetermine the potential off-site consequences of a release. Some HAZMAT(Hazardous Materials) vehicles also contain portable computers loadedwith software to calculate and plot air dispersion modeling on an areamap to accurately define impacted areas. These tools assist theidentification and mitigation planning for fire departments andemergency responders during hazardous chemical releases. However, inorder for these agencies to take appropriate actions, including orderingevacuation or sheltering-in-place, the agency must be able to achieveprompt community notification. Unfortunately, community notice ofevacuation and sheltering-in-place, can only be achieved by broadcastnotification and/or door to door notification. However, as noted above,broadcasting requires the attention of local citizenry, and furthermore,door-to-door notification is time consuming and potentially dangerous toemergency personnel.

As has been shown, current reliance upon local media and supplementalNWR broadcasts are insufficiently effective in notifying individualswhen danger threatens life or property. Citizens must always have theirTV on and they must be watching; or their radio must be turned on andthey must be listening for a broadcast alert to be effective. There isthus a compelling need for an alert notification system that is designedto always be available whenever the need arises, a notification systemthat can not be turned off (short of termination of service). Thissystem should not require the notification recipient purchase anyadditional equipment and the system should deliver an alert signal withwhich we have all been instinctively trained to respond. It is alsoimportant that the alert notification system have the ability topinpoint, calculate and define dynamically all recipients with respectto their notification requirements then systematically notify thoseindividuals (and only those individuals) within those defined geographiclocations. The system must provide the notification quickly andaccurately, with the ability to track the progress of the notificationprocess and provide scenario resolution status until the notificationscenario is completed or until the alert has expired.

SUMMARY OF THE INVENTION

The invention described in this patent application satisfies thesefundamental needs. The invention builds from the recognition thatvirtually every office and home already includes a communication devicethat meets the above-stated requirements: it is always turned on, itproduces a recognizable alert signal upon remote command, and citizenshave been trained to respond to this signal under all circumstances. Thedevice is the telephone. Utilizing principles of the present invention,anyone near to a telephone (including a wired or cellular telephone) canbe notified of an emergency or alert that directly threatens or is ofinterest to him or her.

Although the specific embodiment of the invention described below isprimarily directed to delivery of warnings via telephone, principles ofthe present invention are equally applicable to the use of othercommunications devices which may eventually become as popular as thetelephone, such as computer -networks, pagers, or other devices.

According to principles of the present invention, warnings such asweather or other emergency condition notifications, are provided tointerested individuals by selecting from a database, communicationsidentifiers (e.g., telephone/pager/facsimile numbers, computer networkaddresses such as Internet e-mail addresses or IP addresses),establishing communication connections using the identifiers, and thendelivering an appropriate warning via the connection, which may or maynot include information about where to find additional information.

In one disclosed embodiment, persons are selected in accordance with thephysical location of the threat. To provide geographically-basednotifications, the system registers the physical location for everycommunications identifier, based upon (among other possibilities) acounty, city, area code, exchange, zip code, and/or global positioningcoordinates (GPS). The degree of specificity used depends upon thespecificity of the alert to a particular population or location. Forexample, storms will move with a particular trajectory and speed. Ahazardous chemical fire will release a toxic cloud that will followprevailing winds. The threat of a gas main explosion may require theevacuation notification with a specific mileage radius around one GPScoordinate or street address.

While the specific embodiment of the invention described below isprimarily directed to geographically-based selection of communicationsidentifiers, based upon identification of atmospheric conditions such asweather, toxic releases or other air quality conditions, principles ofthe present invention are equally applicable to delivering other kindsof warnings. For example, warnings of school closures, trafficconditions and other closures, interruptions or schedule changes canalso be provided to interested parties in accordance with principles ofthe present invention. In such cases, the information registered foreach communication identifier is sufficient to determine whether thatidentifier should be warned of a particular event, and when such anevent occurs, and an appropriate warning is delivered.

This system will thus “intelligently” provide notification to selectedpopulations of citizens in a short period of time, based on specificcriteria such as the location or type of situation, or the current orpredicted movements of a threat. Furthermore, unlike the unsuccessfulsystems of the past, this system will track the notification process andcall recipient responses, so it can then repeatedly attempt to notifyall persons or locations until a response is registered, or theemergency expires or terminates based on a specific escalation scenario.This system can target specific locations or specific individuals, orboth, based on the type of alert that is being generated. The systemtracks every notification, re-contacts failed attempts, automaticallyexecutes a specific execution scenario dependent upon the alertrequirements and delivers specific emergency information. Importantly,the system leaves uninterested citizens undisturbed, thus avoiding a“Boy Who Cried Wolf” problem.

The above and other objects and advantages of the present inventionshall be made apparent from the accompanying drawings and thedescription thereof.

BRIEF DESCRIPTION OF THE DRAWING

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate embodiments of the invention and,together with a general description of the invention given above, andthe detailed description of the embodiments given below, serve toexplain the principles of the invention.

FIG. 1 is a diagram of a system in accordance with principles of thepresent invention, having facilities for detecting alert conditions anddistributing alert notifications.

FIG. 2 is a sample text file from EMWIN Data Stream.

FIG. 3 is an illustration of the database tables used by the system ofFIG. 1, and

FIGS. 3A through 3C are detailed illustrations of each of the tables inthe database.

FIG. 4A is a flow chart of the operations of the Notification ParsingSystem in accordance with principles of the present invention;

FIG. 4B is a flow chart of the operations of the IVR AdministrativeSystem in accordance with principles of the present invention;

FIG. 4C is a flow chart of the operations of the IVR SubscriberRegistration System in accordance with principles of the presentinvention;

FIG. 4D is a flow chart of the operations of the Web ServerAdministrative System in accordance with principles of the presentinvention;

FIG. 4E is a flow chart of the operations of the Web SubscriberRegistration System in accordance with principles of the presentinvention;

FIG. 4F is a flow chart of the operations of the Database Query Systemin accordance with principles of the present invention;

FIG. 4G is a flow chart of the operations of the Web Server inaccordance with principles of the present invention;

FIG. 4H is a flow chart of the operations of the Switch Host inaccordance with principles of the present invention;

FIG. 5A is an illustration of a Static Area Notification scenario, and

FIG. 5B is an illustration of specific operations performed by theDatabase Query System in handling this scenario;

FIG. 6A is an illustration of Radius Notification scenario, and

FIG. 6B is an illustration of specific operations performed by theDatabase Query System in handling this scenario;

FIG. 7A is an illustration of Vector Notification scenario, and

FIG. 7B is an illustration of specific operations performed by theDatabase Query System in handling this scenario;

FIG. 8A is an illustration of a Shoreline Notification scenario, and

FIG. 8B is an illustration of specific operations performed by theDatabase Query System in handling this scenario;

FIG. 9A is an illustration of a River or Flood Plane Notificationscenario and

FIG. 9B is an illustration of specific operations performed by theDatabase Query System in handling this scenario;

FIG. 10A is an illustration of a Wind Dispersion Notification scenarioand

FIG. 10B is an illustration of specific operations performed by theDatabase Query System in handling this scenario.

FIG. 11 is an illustration of specific operations performed by theDatabase Query System in handling a School/Organization alert.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

FIG. 1 illustrates an alert notification system in accordance with theprinciples of the present invention. At the core of alert notificationsystem 100 is a network of computers connected via computer networkconnection 102.

The computers on network 102 include a database server 104 for storing adatabase of information detailed below in connection with FIGS. 3, 3A,3B and 3C. This database is utilized by other systems on network 102 toevaluate alerts and to deliver alert notifications to appropriatepersons.

Connected to database server 104 via network 102 are three additionalcomputers. The first computer system is a Notification Parsing System106, which is connected to a receiver 108 that receives continuous datafeeds from a satellite 109 and/or is connected to a radio receiver(e.g., an FM receiver 110) that receives continuous data feeds from aradio transmitter 111. Notification parsing system 106 may be programmedto evaluate notifications delivered by any one of a variety oforganizations via anyone of a variety of communications mechanisms. Forexample, in addition to satellite and radio broadcasts, NPS 106 may alsoreceive information via Internet dissemination. In the followingdescription of an embodiment of the present invention, NPS 106 isresponsible for receiving National Weather Service EMWIN data streamsreporting weather conditions and other critical information. As furtherdata streams become available via satellite, radio or Internet media,these additional data streams may be parsed by NPS 106 in a manneranalogous to that described below.

Computer network 102 is also connected to a database query system 112.Database query system 112 interacts with database server 104 in responseto messages received from other computers, to evaluate alert conditionsand determine appropriate recipients of alert information. Databasequery system 112 receives data packets from notification parsing system106 and from a web server 114 connected to the Internet 115, and from anIVR system 116 that can be contacted from remote telephones 117. Thesedata packets take the form shown in Table I.

TABLE I Field Name Size Format Notification Event 9 Numeric NotificationID 4 Numeric Priority Level 2 Numeric State 2 Character County 3 NumericCity 3 Numeric Zip Code 9 Numeric Expiration Time 8 Time Expiration Date8 Date Location Zip Code 9 Numeric Location Latitude 9 Float LocationLongitude 9 Float Radius 3 Numeric GPS Coordinates 9 Numeric Heading 3Numeric Speed 3 Numeric Timeframe 3 Numeric Bands 2 NumericSchool/Organization ID 9 Numeric

As seen in Table I, data packets include a variety of fields each foridentifying particular information. Notification event is a nine bytefield holding a numeric value indicating the type of notification thatis being delivered. Notification ID is a four byte field holding anumeric value uniquely identifying the notification so that it can bedistinguished from others of the same type. Each notification event,therefore, can be uniquely identified and tracked through archivedinformation, as discussed further below. Priority level is a two bytefield storing a numeric value indicating the priority of thenotification. All notifications will include notification event,notification ID and priority level values. Furthermore, all alerts willinclude an expiration time value in an expiration time field, stored asan eight byte time formatted value. Furthermore, all alerts will includean expiration date stored in an expiration date field, stored as aneight byte date formatted value.

The additional fields shown in Table I, are used to specificallyidentify the location or circumstances of the alert, and may not all beused in any given alert. A State field includes two bytes of characters,providing a state code for the location of the event. A County fieldincludes a three byte numeric value identifying a particular county. ACity field includes a three byte numeric value identifying a city, and aZip code field includes a nine byte numeric value identifying a zipcode. An alert relating to a specific geographic location, such as astatic area alert, will include one of a state, county, city or zip codevalue which will geographically reference the static area to which thealert applies.

Radius alert events are identified by reference to a specific geographiclocation and radius surrounding that location. For these events, alatitude and longitude will be stored in a location latitude field and alocation longitude field, both of which carry nine byte floating pointnumeric values. As an alternative to a latitude and longitude, a radiusevent may store global positioning system (GPS) coordinates as a ninebyte numeric value in a GPS coordinates field. Radius events will alsostore a radius value in a radius field as a three byte numeric value.

Vector alerts identify an area to be alerted utilizing a vectorizeddescription of the location of the condition. These alerts will identifya heading in three byte numeric heading field, a speed in three bytenumeric speed field and a time frame in a three byte numeric time framefield. Furthermore, for the purposes of processing these alertconditions, vector related alerts will also identify a number of bandsused in processing the alert; this number of bands will be stored as atwo byte numeric value. Vector related alerts will also include locationinformation, for example, one of a zip code, latitude and longitude orGPS coordinate value.

Shoreline or river related alert notifications will carry informationsimilar to static area alert notifications, i.e., a state, county, cityand zip code identity.

A last category of alert is a school/organization alert, used to notifystudents/parents of a school cancellation/emergency or analogouslynotify members of an organization of a cancellation/emergency orschedule change. To facilitate such alerts, a School/Organization IDfield holds a nine byte numeric value identifying a school (or schooldistrict) or organization. A school or organization related alert willidentify the subscribers needing notification, using theschool/organization ID number stored in this field.

Alerts are received by database query system 112 through a variety ofchannels and take different forms. Weather related alerts includingflood alerts and other alert conditions identified by the NationalWeather Service are provided by notification parsing system 106 todatabase query system 112.

Referring to FIG. 2, it can be seen that a text file 118 produced fromthe EMWIN data stream includes a number of fields that can be readilyparsed by notification parsing system 106. The first line “WFUS1 KIWX010238” is a “WMO” header that includes a 4-6 character productidentifier, a 4 character source site code, and a GMT formatted 6-digitorigination time. The subsequent lines of the EMWN data stream includetext information and codes, as well as, in some cases, graphic files andother data. Detailed information on the format of the EMWIN data streamsis available from NOAA, e.g. from the URLhttp://www.nws.noaa.gov/oso/cominfo.shtml.

Each EMWIN file includes prefix codes identifying a particular eventthat is the subject of the notification. As can be seen in FIG. 2, thenotification code of TOR 120 in the second line of the file, is used toidentify a tornado warning. Notification parsing system 106 identifiesthis product code and uses it to generate an appropriate packetutilizing the format of Table I. Notification parsing system 106 alsoparses the remainder of the text file to identify geographic locations.These may be coded using “Universal Generic Code”, e.g., including thecounty identifiers INC141 and INC099 (or the subsequent text 122) shownin FIG. 2, which identify St. Joseph County and Marshall County in northcentral Indiana. County identifiers are coded using the FederalInformation Processing Standard (FIPS 6-3), under which each county hasa 3-digit identifier. The identified county information can be enhancedby parsing the subsequent text, which as shown at 122 indicates that thealert condition is specifically for southwestern St. Joseph County andextreme northwestern Marshall County.

Furthermore, notification parsing system 106 may identify headinginformation such as, at 124, the text indicating that the tornado ismoving northeast at 40 mph. The alert time and alert ending timeinformation, available in GMT format (“010238” and “010305”), and in atext format, can be used to identify a time period for the alert.Notification parsing system 106 may also utilize the listing of affectedtowns at 126 to identify zip codes of those locations and therebyproduce alert notifications based upon zip codes. Furthermore, the bodyof the NWS message may also be inserted into a facsimile message, sentas an electronic mail message, read via a computer-generate voice overthe telephone, or forwarded to a text pager.

Table II, appearing below, summarizes the prefix codes utilized in EMWINdata streams and the meanings of those prefix codes. Each particulartype of alert will be converted to alert messages if an appropriate typecan be gleaned from one or a collection of EMWIN data stream segments.

TABLE II Prefix Name AFD Area Forecast Discussion AIR Upper Air (Data)APT Polar Orbiter Images ASH Volcanic/FIRE Warnings and reports AWS AreaWeather Summary CEM Civil Emergency Message CFW Coastal Flood WarningCHT Charts DIFAX/WEFAX CLI Climate Reports CMP Composite Images(CMPALLUS.GIF) CMP Compressed Files (CMPMxxxx.ZAG) CWF Coastal WatersForecast DY1 Day One Convective Outlook DY2 Day Two Convective OutlookELN El ‘Nino images EMA Emergency manager activation msg. EML Email(wireless) EPH Ephemeris data for satellite orbits EQR Earthquake DataESF Flood Potential ESS Water Supply Forecast FAA Aviation Reports(Pilot briefs) FEE Feedback to all users FFW Flash Flood Warning FFAFlash Flood Advisory FFS Flash Flood Statement FLN National FloodSummary FLW Flood Warning FWF Fire Weather Forecast GLF Great LakesForecast GLO Great Lake Outlook GLS Great Lakes Summary GMS GMSSatellite Images GO9 GOES 9 Satellite Images G10 GOES 10 SatelliteImages GPH Graphic Files (AFOS Graphics) HAA Hurricane ProbabilitiesAtlantic HAD Hurricane Discussion Atlantic HAF Hurricane ForecastAdvisory Atlantic HAM Hurricane NCEP Model Comparison Atlantic HAPHurricane Public Advisory Atlantic HAS Hurricane Monthly SummaryAtlantic HAT NCEP Tropical Discussion Atlantic HAW Tropical WeatherOutlook Atlantic HEA Hurricane Probabilities East Pacific HED HurricaneDiscussion East Pacific HEF Hurricane Forecast Advisory East Pacific HEMHurricane NCEP Model Comparison East Pacific HEP Hurricane PublicAdvisory East Pacific HES Hurricane Monthly Summary East Pacific HETNCEP Tropical Discussion East Pacific HEW Tropical Weather Outlook EastPacific HFF High Seas Forecast HLS Hurricane Local Statement HNAHurricane Probabilities North Pacific HND Hurricane Discussion NorthPacific HNF Hurricane Forecast Advisory North Pacific HNM Hurricane NCEPModel Comparison North Pacific HNP Hurricane Public Advisory NorthPacific HNS Hurricane Monthly Summary North Pacific HNT NCEP TropicalDiscussion North Pacific HNW Tropical Weather Outlook North Pacific HSAHurricane Probabilities South Pacific HSD Hurricane Discussion SouthPacific HSF Hurricane Forecast Advisory South Pacific HSM Hurricane NCEPModel Comparison South Pacific HSP Hurricane Public Advisory SouthPacific HST NCEP Tropical Discussion South Pacific HSS Hurricane MonthlySummary South Pacific HSW Tropical Weather Outlook South Pacific HWAHurricane Probabilities West Pacific HWD Hurricane Discussion WestPacific HWF Hurricane Forecast Advisory West Pacific HWM Hurricane NCEPModel Comparison West Pacific HWP Hurricane Public Advisory West PacificHWS Hurricane Monthly Summary West Pacific HWT Hurricane NCEP TropicalDiscussion West Pacific HWU Hazardous Weather Update HWW TropicalWeather Outlook West Pacific HTM HTML Documents ICE Ice Statement IMGGeneral Images (IMGALLUS.GIF) INT International Overviews LFP LocalForecast LGT Lightning Images LSH Lake Shore Forecast LSR Local StormReport MET Meteosat Images MIS Miscellaneous Products MOD Model RunImages MWS Marine Weather Statement NAH Agriculture Products (Intn'l/National) NSH Near Shore Forecast NOW NOWcasts (Short Term Forecast)NPW Non-precipitation Warning NWX National Weather Summary OFF OffshoreForecast OMR Other/Offshore Marine Reports PAA Pager Messages PNS PublicInformation Statements PRO Propagation Reports PSR Post Storm Report RADRadar Images (RADALLUS.GIF) REC Recreation Forecasts RER Record EventReports RFW Red Flag Warning (Fire Warning) RVA River Summary RVR RiverForecast RVS River Statement RWS Regional Weather Summary SAH SurfaceObservations (Data) SAO SAORCMUS.TXT Contains RCM's SAW Selected AreaWatches SCS Selected cities (scs11-scs14) SEL Watch areas SESSeismic/Earthquake Images SFD State Forecast Discussion SFP StateForecast SHP Live Ship Reports SIX Six to Ten day outlook SLS Arealupdate SKY SKYWARN Activation Message SMW Special Marine Warning SPSSpecial Weather Statement STP State Temp & Precip Reports SUM StateWeather Summary SVR Severe Thunderstorm Warning SVS Severe WeatherStatement SWO Severe Weather Outlook SWR State Weather Roundup SWX SpaceWeather (solar activity) SYS System messages TAF Aviation TerminalForecasts/airports TID Tide Data TOR Tornado Warning TRK Tracking Files(storm tracks) TSU Tsunami TVL Travelers Forecasts LVI NationalUltra-Violet index WSW Winter Storm Warning WWA Weather Watch ZFP ZoneForecast

Returning now to FIG. 1, in addition to the EMWFN system, alertconditions may also be identified by individuals authorized to initiatethe delivery of alerts through the alert notification system 100.Authorized individuals may include civil defense authorities in the caseof civil emergencies, school administrators in the case of schoolrelated alerts, and managerial employees of business or communityorganizations that wish to utilize the system of FIG. 1, viaorganization alerts.

Alerts initiated by these authorized individuals may be delivered to thesystem 100 via an interactive voice response system 116 which can beaccessed via any telephone. Alerts may also be delivered via an Internetconnection, for example using a World Wide Web browser connected viahypertext transfer protocol (HTTP). In this case, connections are madethrough the Internet to web server 114 to generate an alert message.

Alerts generated using web server 114 or IVR server 116 are delivered todatabase query system 112 through packets which are also formatted inaccordance with Table 1. Database query system 112 then identifiessubscribers to be individually alerted, and then alert notifications aredelivered to subscribers, via telephone, via facsimile, via electronicmail or via other electronic communications.

Telephone and facsimile alerts are delivered to subscribers through aswitch host computer 130 and a host controllable switch 132. Switch hostcomputer 130 is connected to host controllable switch 132. Switch 132 isa host controllable switch that interfaces with digital telephone lines134 of a telecommunications carrier to permit outbound telephone callsto be generated at a high volume, to be delivered to subscribers to thesystem 100. Outbound telephone calls from host controllable switch 132are routed through the public switched telecommunications network 136 totelephones subscribed in system 100, such as wired telephones at privatehomes and businesses, as well as cellular telephones. Outbound telephonecalls from host controllable switch 132 may also connect to facsimilemachines to deliver facsimile alert messages.

As can be seen in FIG. 1, switch host 130 and host controllable switch132 can be utilized to handle multiple alerts from multiple locationssimultaneously. As can been seen in FIG. 1, an evacuation alert using aradius pattern is being delivered to a region 140 in the state ofWashington; simultaneously, an alert related to an earthquake warning isbeing delivered to a region 142 in the state of California; a radiationleak wind dispersion alert is being delivered to a region 144 in thestate of Texas; a flood or high wave condition alert is being deliveredto a shoreline region 146 in the state of Florida; a weather alert isbeing delivered to a region 148 in the state of Ohio; and a biohazardrelated alert is being delivered to a region 150 in upstate New York.

The system illustrated in FIG. 1 is scalable such that any quantity ofalerts to any geographic regions can be handled by simply enhancing thecapacity of host controllable switch 132. Such enhancement is within theknowledge of those of skill in the art of telephony. Accordingly, anationwide or even global alert notification system can be implementedat a single geographic location using the principles of the presentinvention.

To ensure high reliability and robustness, in accordance with theprinciples of the present invention, the system 100 may be redundantlypositioned at multiple geographical locations. Thus a second redundantreal time tandem system 100 with an analogous configuration, may belocated at a separate geographic location and connected via a point topoint data connection 160 to the system 100 illustrated in FIG. 1.Systems 100 and 100′ are in continuous communication over point to pointlink 160 to insure that all alert notifications are received by bothsystems, and thereafter one system is tasked with handling eachnotification. The systems also continuously communicate to maintainsynchronization of the databases handled by the respective databaseservers of the respective systems. In the event of a failure at one ofthe tandem systems, all existing requests for alert notification will behandled by the other system to insure that the alerts are deliveredappropriately in spite of the network failure.

As noted above, telephone and facsimile communications are delivered totelephone and facsimile machines via host controllable switch 132. Alertnotifications may also be delivered via electronic mail or otherInternet communication methodologies. In this case, the alertnotification is handled by web server 114. In such a scenario, databasequery system 112 instructs web server 114 to deliver the alertnotification, and in response web server 114 connects via its Internetconnection to the appropriate location to deliver the alert.

Table III, which appears below, illustrates the format of packetstransferred from database query system 112 to switch host 130 and webserver 114 to cause an alert to be delivered.

TABLE III Field Name Size Format Priority Level 2 Numeric NotificationEvent 9 Numeric Station ID 30  Character Station ID Type 2 NumericMessage ID 1 4 Numeric Message ID 2 4 Numeric Message ID 3 4 NumericMessage ID 4 4 Numeric

As seen in Table III, packets sent from database query system 112include fields for specifically identifying the recipient of an alertand the type of the alert. The first field, “priority level” includes atwo byte numeric value indicating a relative priority of the alertmessage. This value is derived from priorities assigned to alertsdelivered to database query system 112 by notification parsing system106 or web server/IVR system 114, 116. A second field, “notificationevent”, includes a nine byte numeric value having a numeric code for thetype of alert that is being delivered. A third field, “station ID”includes a 30 byte character value that identifies the recipient of thealert notification. In the event that the alert is being delivered viatelephone or facsimile, the station ID field will include a telephonenumber. In the event that the alert is being delivered via electronicmail or the Internet, the station ID will include an electronic mailaddress or a uniform resource location (URL) indicating where the alertis to be delivered. A “station ID type” field includes a two bytenumeric value identifying the type of station ID that is provided in thepreceding field. Thus alerts to telephones can be distinguished fromalerts to facsimile machines, from alerts to electronic mail addressesand from alerts to other IP or similar computer network addresses.

After these fields are four message ID fields, each of which is a fourbyte numeric value. These fields contain a code for a message to bedelivered to the subscriber/recipient of the alert. Multiple messagesmay be delivered simultaneously; to facilitate this, four message IDsmay be supplied in single packet as illustrated in Table III. Themessage IDs may be an index usable by host controllable switch 132 toretrieve a voice message to be delivered via telephone, or may be anindex to a prestored facsimile message to be delivered to a facsimilemachine. In the case of alert notifications to be delivered to email orInternet addresses, each message ID will be an index to prestored textfor the email message or prestored text or other actions to be performedat a web site or other resource accessible via the uniform resourcelocator.

Referring now to FIG. 3, the databases utilized by the system of FIG. 1are generally illustrated. These databases are stored and managed bydatabase server 104. Notification parsing system 106 and database querysystem 112 retrieve data from these databases as needed to perform thefunctions discussing generally above and elaborated below.

Tables 170 and 172 managed by database server 104 are used bynotification parsing system 106 in parsing EMWFN data streams from theNational Weather Service. The notification parsing system 106 parsesdata received from these data feeds to identify text, graphic and imagefiles. Each file is then processed to determine its file type. The filetypes listed in Table I are stored in notification table 170.

The detailed format of notification table 170 is shown in FIG. 3A. Eachrecord of the notification table 170 includes a product ID field 174which is a three byte character value in the formats shown in Table Iabove. A second field 176 stores a two byte numeric value identifying apriority level for the product or event type represented by the record.A third field 178 stores a 4 byte numeric value providing a notificationidentifier associated with the product represented by the record. Thenotification identifier maps to one of the predefined notificationshandled by the system, and is used when delivering a correspondingpacket in the format illustrated in Table 2 from the notificationparsing system to the database query system.

FIG. 3B illustrates a priority table 172 which provides specificinformation about priority levels identified in field 176 of thenotification table 170. Each record in the priority table 172 includes apriority level field 180 for storing a two byte numeric valueidentifying a priority level. Each priority table record includes aresource utilization field 182 for storing a percentage value indicatingthe amount of resources of the system that are to be consumed for analert at the identified priority level. The resource utilizationpercentage identified in field 182 is used in determining the extent towhich a given alert should be allowed to consume all of thecomputational resources of database query system 112 and/or switch host130 and line capacity of host controlled switch 132.

FIG. 3 also illustrates a variety of subscriber related tables 184, 186,188, 190, 192 and 194. These tables are used to store informationrelating to subscribers to permit database query system 112 to identifyspecific subscribers to receive alert notifications in response topackets received from web server 114, IVR system 116 or notificationparsing system 106.

Referring now to FIG. 3C, the schema of these tables 184-194 can beviewed in detail.

The subscriber information table 184 includes information regarding asubscriber that is useful for determining whether that subscriber shouldbe notified of an alert condition. Each record in the subscriberinformation table 184 includes a field 200 providing a customer numberor customer identifier for this subscriber. This unique identifier isused to link information about a subscriber in table 184 to informationabout the same subscriber in the other tables 186, 188, 190, 192 and194. Subscriber information table 184 also includes extensiveinformation regarding the subscriber to be used in contacting thesubscriber. For example, a field 202 is used to store a telephone numberor ANI used to contact the subscriber. A field 204 includes anelectronic mail address for the subscriber. A field 206 includes anInternet, i.e., TCP/IP address for the subscriber. Typically asubscriber will have only one mode of contact, i.e., only one of thethree fields 202, 204 and 206 will include a value. However, asubscriber may also have multiple modes of contact registered (see table192, discussed below) in which case the appropriate mode of contact ischosen based upon the priority of the alert, the type of the alert orsubscriber preferences.

Continuing on the subscriber information table 184, the table includesfields for identifying information regarding the subscriber that can beused to determine whether the subscriber ought to be notified of a givenalert condition. These fields include a field 208 for storing a postalzip code for the subscriber, a field 210 for storing the countyidentifier for the subscriber, a field 212 for storing a stateidentifier for the subscriber and a field 214 and a field 216 foridentifying a latitude and longitude for the subscriber. Fields 208through 216 identify at varying levels of specificity the geographiclocation of the subscriber so that the subscriber can be selected forreceipt of a notice under the appropriate conditions. Other informationmay also be used to determine whether a subscriber should be contacted.For example, a school district name and a school organization ID arestored in fields 218 and 220 to affiliate the subscriber with a schoolor organization that may need to inform pupils or organization membersof cancellations or changes utilizing the alert notification system ofthe present invention. A field 222 is used to store an elevation at thesubscriber's location and a field 224 is used to store a flood zone codefor the subscriber. These fields will be used to identify whether thesubscriber is subject to alert notifications relating to floods orweather conditions that only affect certain elevations or flood zones. Afield 226 may also be used to classify the location of the subscriber inother ways, for example nearness to open space or trees where winddamage may be more likely, or location within an office building atwhich shelter may be more difficult to find. A field 228 includes codingrelating to the construction of any building associated with thesubscriber. A field 230 is used to identify the number of levels in thebuilding associated with the subscriber. Fields 228 and 230 can be usedtogether to prioritize the danger to a subscriber arising from a weathercondition or any other condition that may be more dangerous to someforms of building construction or some heights of buildings. A field 232is used to generally classify any special needs of the subscriber thatmay be applicable in determining the priority to be given alerting thesubscriber of conditions monitored by the system. These conditions mayinclude the need to use a wheelchair or personal assistance to seekshelter in the basement of the subscriber=s location. Fields 234, 236,238 provides an indication of the number of persons potentially at riskat the location identified in the record. Field 234 provides a count ofadults at that location, field 236 provides a count of the number ofelderly persons in that location and field 238 provides a count of thenumber of children in that location. Alert notifications may beprioritized to reach the largest population of persons most rapidly ormay be prioritized to reach locations where there are children orelderly citizens more rapidly in order to provide the requiredadditional time to take shelter. Additional fields 240 and 242 are usedto determine whether a subscriber should receive priority foratmospheric condition alerts, or is interested in such alerts at all.Field 240 indicates that a subscriber has a respiratory condition of thekind that would be affected by ozone alerts or other respiratory-relatedweather conditions that may adversely impact only those members of thepopulation with respiratory conditions. A field 242 will be used toidentify allergic conditions of persons at this subscriber location suchthat alert notifications may be provided to indicate the presence ofallergens of a particular kind in the atmosphere. A field 244 indicateswhether the 1 subscriber location is capable of receiving broadcasts ofweather or other alert information. The subscriber may be placed in ahigher priority if the subscriber is not able to receive alertnotifications via other broadcast media. The field may also indicatethat the subscriber is, itself, a “broadcaster”, i.e., a party thatrelays alert information to further persons. A “broadcaster” is alsoprovided with enhanced priority to assist in fulfilling broadcastresponsibilities and to ensure the greatest number of persons arenotified of the alert as soon as possible. Field 244 may also be used to“brand” the alert notification, e.g. by identifying a broadcast stationthat sponsors the delivery of the alert notification, so thatsubscribers develop goodwill for the sponsoring station and turn to thatstation for additional information. A field 246 indicates whether abasement is available at the subscriber location aiding and prioritizingsubscribers who do not have access to sufficient shelter over othersubscribers who do have access to sufficient shelter within their ownhomes. This, for example, would allow alerts to be delivered first tomobile home parks and other (high risk) areas that are particularlysusceptible to weather damage. A field 248 indicates whether thesubscriber location has an answering machine and a field 250 indicatesthe ring count for the answering machine. These fields are used to avoidleaving a message on an answering machine or voice mail service if thereis such a service in use at the subscriber's location. The ring count isused to ensure that the host controlled switch will disconnect prior toreaching the identified number of rings, so that the answering machineor voice mail system will not pick up the line. As a consequence, thesubscriber's location will be called repeatedly until an answer isreceived, thus ensuring that the alert message is delivered to a personrather than to an answering machine or voice mail system.

The final two fields 252 and 254 are useful in managing the delivery ofinformation to the subscriber. Specifically, field 252 stores theidentifier for the last notification that was provided to thesubscribers location, and can be used as a confirmation that anotification was given to the subscriber with respect to that condition.A retry Count found in field 254 is used to control the number of timesa subscriber location is contacted to attempt to deliver emergencyinformation. A subscriber may wish to set a retry count value based uponpreference and knowledge of the subscriber's ability to consistentlyanswer telephone calls during a known period of time.

The subscriber billing table 186 stores information used in invoicing asubscriber for services provided by the alert notification system. Afield 260 the subscriber billing table 186 is used to store a customernumber, i.e., customer identifier for a subscriber to thereby relate thesubscriber to the other tables illustrated in FIG. 3C. A subscriberbilling table 186 provides information needed to appropriately bill asubscriber for services provided by the system. These fields include afield 262 for storing a first name, a field 264 for storing last name,fields 266 and 268 for storing two lines of physical addresses for thesubscriber, a field 270 for a city, a field 272 for a state and a field274 for a zip code. Additional fields are used to provide a billingaddress if needed for the subscriber including a field 276 for name,fields 278 and 280 for a billing address, a field 282 for a city, afield 284 for a state and a field 286 for a zip code. A field 288identifies a billing method preferred by the subscriber, such as advanceinvoicing or alternatively automatic payments via credit card. A field290 identifies the billing period preferred by the subscriber, such asweekly, monthly or annually Discounts may be provided for prepayment oflarge subscription periods. Fields 292 and 294 identify starting andending dates for service provided by the system during a current billingperiod. Fields 296 and 298 provide a credit card number and expirationdate to be used in billing the subscriber. Fields 300, 302, 304 and 306provide name and address information for a credit card to be used inbilling the subscriber in advance via credit card. This information mustbe stored to insure payment by the credit card company for chargesbilled. Fields 308, 310 and 312 store automated clearinghouse (ACH)information for the customer, which may be used to generate ACHtransactions to automatically invoice the customer for payments forservices provided by the system.

Subscriber census table 188 stores information relating to persons atthe location identified in the subscriber information table 184.Subscriber census table records include a field 320 for storing customeridentifier to link the record to subscriber information in subscriberinformation table 184. Subscriber census table 188 also includes fields322 and 324 for storing a first and last name for a subscriber, and anage field 326 for storing an age of a subscriber. It will be appreciatedthat a given subscriber location may be inhabited by multiple persons inwhich case there are multiple subscriber census table 188 entries, onefor each person, so that information about the multiple persons may bestored and retrieved and used to customize alerts. Furthermore,subscriber census information can be used to provide census data toemergency agencies via telephone, facsimile, e-mail, or other media.This information can facilitate rescue efforts and further define theimpact of an emergency condition on local emergency response services.For example, in the case of an explosion, census information can be usedto define population impact, aid in targeting the search for survivors,and defining an evacuation scale. For the case of a biohazardouscondition, census information can aid in defining the amount of medicalservices that will be consumed in treating victims.

Subscriber notification preferences table 190 is used to identifypreferences of a subscriber with respect to notifications by the system.A field 330 is used to store a customer identifier to link thepreferences identified in table 190 in the subscriber information table184. Additional fields in the subscriber notification preferences table190 include a field 332 for storing a notification type and fields 334and 336 for identifying a start hour and minute and fields 338 and 340for identifying an ending hour and minute. A record in subscribernotification preferences table 190 can be used to identify the hoursduring which an alert notification should be sent to a given subscriberlocation. Thus, a subscriber may request that atmospheric conditionalerts that are not immediately hazardous, such as ozone alerts, not benotified to their home location during the nighttime when residents ofthe home will be sleeping and not traveling outdoors. It will be notedthat each record in subscriber notification preferences table 190relates to a particular notification type and a particular subscriber.Thus there may be multiple preference records in table 190 for a givensubscriber, one record for each type of notification for which thesubscriber has indicated preferences.

Subscriber alternate contact table 192 is used to provide additionalcontact information for subscribers. Each record in table 192 includes afield 350 for identifying a customer identifier to link the alternatecontact information to the subscriber information table for thesubscriber. Each record in the subscriber alternate contact table 192includes fields 352, 354 and 356 for identifying a telephone number orANI, an email address and TCP/IP address. Through the use of alternatecontact records in alternate contact table 192, multiple contact pointsmay be entered into the database for a given subscriber so that asubscriber may contacted at, for example, multiple phone numbers at agiven location or at a phone number and at a cellular telephone number,or at multiple email addresses.

Subscriber history table 194 is used to store historic information onalerts delivered to a subscriber for the purposes of auditing alerts,and potentially for billing subscribers on an alert basis. Each recordin subscriber history table 194 includes a customer number (customeridentifier) field 360 for linking the record to other subscriberinformation in the database. Each record also includes additional fieldsfor providing historical information on a type of notification which wasdelivered or attempted to be delivered to the subscriber. Thisinformation includes a date and time stored in fields 362 and 364 and atype of notification stored in field 366. A notification identifierwhich uniquely identifies the notification stored in field is stored infield 368. Field 370 provides a communications addresses used to attemptto notify the subscriber of the condition, and field 372 indicateswhether the alert was successfully completed. It will be appreciatedthat a given subscriber may receive multiple alerts from the system overthe passage time and therefore a subscriber will have multiple recordsthat will appear in subscriber history table 194, one for each alert orattempted alert to the subscriber that has been historically provided.It will also be appreciated that a subscriber history table record willbe generated each time an alert is attempted to a subscriber and thatrecord will be updated to indicate whether the attempt was successfullycompleted and the type identifier and communications addresses used inattempting the alert notification.

Referring now to FIG. 4A, the process for parsing EMWIN data feeds atthe notification parsing system 106 can be explained in further detail.In a first step 400, the data feeds from FM receiver 110 and/orsatellite receiver 108 are initialized. Then in step 402, notificationparsing system 106 waits for data from the initialized data feed. Whendata is received, in step 404 the data is read until an END OF FILE codeis reached. (An END OF FILE code can be seen in FIG. 2 at the end of thetextual information.) In a subsequent step 406, the National WeatherService product ID for the feed is determined. This product ID can beseen at 120 in FIG. 2. In subsequent step 408 a database record isretrieved from the notification table 170 of FIG. 3A that has a productID in field 174 matching the product ID of the received data. In step410 it is determined whether a record exists in the notification table.If not, then in step 412 the received file is archived and thenotification parsing system 106 returns to step 402 to wait foradditional data.

If a record is found in step 410, then in step 414 the received datafile is parsed for the notification type and affected area. This willinvolve pattern matching and text parsing as discussed above withreference to FIG. 2. Subsequently, in step 416 the file is parsed for anexpiration time, current location, heading and speed, if suchinformation is available in the text file. After this information hasbeen collected, in step 418 a data packet (having the format illustratedin Table I) is generated. All pertinent information that has beenobtained from the data stream is included in the data packet. In step420 the data packet is sent to the database query system 112.Thereafter, in step 422, it is determined whether the END OF FILE codehas yet been reached. In some cases, multiple products may be compiledin the same text file. When this occurs, processing will return to step414 to continue to parse the file for additional notifications. When theEND OF FILE is reached in step 422, processing returns to step 402 towait for additional data.

Referring now to FIG. 4B, the processing performed by the IVRadministrative system can be explained in further detail. In a firststep 430, IVR administrative system 116 waits for a call from a user. Instep 432 a user dials into the IVR administrative system; in responsestep 434 the IVR administrative system receives the ANI or caller ID forthe caller from the telephone network. In step 436 the caller isprompted to enter a login identifier and a password using touch tonekeys on their touch tone telephone. In step 438 the ANI, loginidentifier and password collected in the proceeding steps are comparedto those of authorized users of the system. If the ANI, login ID andpassword combination is not found, then in step 440 the caller isnotified that access is denied, and the connection is terminated. If thecaller is authorized, then in step 442 the caller's login ID is used todetermine notification types that the caller is allowed to initiate. Instep 444, the caller is then prompted for a notification type. Thecaller will then provide, using DTMF (touch tone) telephone keys, anotification type number. In step 446 it is determined whether theentered notification type is one that is allowed for the caller. If so,then in step 448 the caller is prompted for relevant information neededto prepare an alert notification. This information may include alocation code, a latitude and longitude, heading and speed informationor other information that is relevant to the type of alert that is to begenerated. In step 450 this information is built into a data packetconforming to the format of Table I. Then in step 452, the packet issent to the database query system 112 for use in generating alerts tothe affected subscribers. Thereafter, in step 454 the caller is promptedfor any additional notifications of affected areas, so that the callermay in rapid succession enter a number of alerts or identify a number ofaffected areas. If the caller, again using DTMF (touch tone) keys,indicates that there are additional notifications or affected areas,processing returns to step 444 to prompt the caller for those additionalnotifications. If the caller indicates that there are no morenotifications or affected areas, or terminates the connection, then instep 456 the IVR administrative system 116 disconnects and then returnsto step 430 to wait for another call.

Returning to step 446, if the notification type entered by the caller isdisallowed, processing continues from step 446 to step 458 in which thecaller is notified that the caller has entered a disallowed notificationtype. Processing then continues to step 454 to permit the caller toenter a new notification if another is desired.

Referring now to FIG. 4C, the process performed by IVR subscriberregistration system to enroll new subscribers can be described ingreater detail. In a first step 460, the IVR subscriber registrationsystem waits for a call from a new subscriber. When a subscriber dialsinto the IVR subscriber registration system in step 462, the IVRsubscriber registration system responds in step 464 by receiving the ANI(caller ID) for the caller from the telephone network. Subsequently, theIVR subscriber registration system in step 466 prompts the caller forall the required information for subscriber information, and the callerdelivers this information via DTMF or touch tone data entry. Thereafter,in step 468 a data packet conforming to Table 1 is built and submittedto database query system 112. This data packet will cause database querysystem 112 to issue a test notification to the new subscriber.Thereafter, the IVR subscriber registration system disconnects in step470 from and returns to step 460 to wait for a new call from another newsubscriber.

Referring now to FIG. 4D, the process performed by web server 114 inreceiving alert notifications can be more fully explained. In the firststep 480, web server 114 waits for an Internet connection. In step 482 auser connects to a web server 114, typically using a hypertext transferprotocol (HTTP) application. In step 484, web server 114 receives anInternet protocol (1P) address for the user from the Internetconnection. In step 486, the user is prompted to enter a loginidentifier and password via a hypertext markup language (HTML) form,otherwise known as a world wide web-based form. After the user hasentered the requested information in step 488, the IP address, login IDand password provided by the user are compared to those of authorizedusers. If this information does not match any authorized user, then instep 490 the user is notified (via a subsequent HTML page) that accessis denied, and the connection to the user's computer is disconnected. Ifthe connection is allowed, then in step 492 web server 114 determinesthe notification text that the user is permitted to create. In step 494the user is prompted again, using the web based form, for a notificationtype. The provided notification type is then evaluated in step 496 todetermine if it is a type allowed by the server for the user. If so,then in step 498, additional web based forms are used to prompt the userfor relevant information for the notification, such as geographicinformation, heading and speed information or other informationdiscussed above. In step 500, a data packet is generated (using theformat of Table I) reflecting the indicated notification type and allprovided information. In step 502 this packet is sent to the databasequery system 112.

Returning to step 496, if the identification type identified by the userin step 494 is not permitted to the user, then the user is notified instep 504 that this notification type is disallowed. After step 504 orstep 502, the user is prompted 506 via web based HTML form, to indicatewhether additional notifications or affected areas are to be entered. Ifthere are additional areas or notifications, the user may indicate assuch by clicking an appropriate area in the displayed form, in whichcase the user is returned to step 494 and prompted for anothernotification type. If the user indicates that no additionalnotifications or affected areas are needed, then in step 508 theconnection to the users computer is terminated.

Referring to FIG. 4E, the process for subscriber enrollment in thesystem via web server 114 can be understood in greater detail. In afirst step 510, web server 114 waits for an Internet connection to bemade by a new subscriber. When a connection is made (step 512), the IPaddress of the user is received from the Internet (step 514) and (step516) the user is prompted to enter required information for subscriptionto the system utilizing a web based form. The information requestedincludes (as described with reference to FIG. 3C), home addressinformation, billing information and other safety or alert preferenceinformation. After this information has been received and stored by webserver 114, a data packet (formatted in accordance with Table I) iscreated in step 518 and sent to the database query system 112. This datapacket causes database query system 112 to initiate a test notificationto the newly enrolled subscriber. After this data packet has been set instep 518, in step 520 the Internet connection to the user isdisconnected and processing returns to step 510 to wait for anothersubscriber to connect to web server 114.

Referring now to FIG. 4F, greater detail can be provided on the processperformed by database query system 112 in response to data packets fromnotification parsing system 106, web server 114 and IVR system 116. In afirst step 530, database query system 112 waits for a data packetformatted in accordance with Table I from the notification parsingsystem 106, IVR system 116 or web server 114. When a packet is received(step 532), the packet is evaluated and the type of notification itrequests is evaluated. Based upon the type of notification, differentactions are performed as explained below with reference to FIGS. 5through 11. If the notification is a static area notification, then astatic area process 534 is performed as is elaborated below withreference to FIGS. 5A and 5B. If the notification is a radiusnotification, then a radius process 536 is performed as elaborated belowwith reference to FIGS. 6A and 6B. It the notification is a vectornotification, then a vector process 538 is performed as elaborated belowwith reference to FIGS. 7A and 7B. If the notification is a shorelinenotification, then a shoreline process 540 is performed as describedbelow with reference to FIGS. 8A and 8B. If the notification is a rivernotification, then a river process 542 is performed as described belowwith reference to FIGS. 9A and 9B. If the notification type is a winddispersion notification, then a wind dispersion process 544 is performedas described below with reference to FIGS. 10A and 10B. If a school ororganization-related alert notification is requested, then a school ororganization alert process 546 is performed as described below withreference to FIG. 11.

The processes 534 through 546 result in generation of stationidentifiers to which alert notifications are to be directed. After theseprocesses are complete (step 550), a first of the selected stationidentifiers is selected, and in step 552 the type of the stationidentifier is evaluated. If in step 554 the station identifier is anemail address, TCP/IP address, or Internet accessible pager, then instep 556 a data packet conforming to Table III above, and including thestation identifier, is sent to web server 114 for ultimate delivery tothe appropriate address. If in step 558 the station identifier is atelephone number or a numeric pager number, then in step 560 a datapacket conforming to Table III above is sent to switch host 130 forsubsequent delivery to the telephone or numeric pager number.Thereafter, in step 562 it is determined whether there is anotherstation identifier that was previously identified in one of theprocesses 534 through 546. If so, then in step 564 the next stationidentifier is selected and processing returns to step 552 to determinethe type of the next station identifier. If in step 562, there is noadditional station identifiers, then in step 566 the received datapacket which began the process is archived and processing returns tostep 530 to wait for another data packet.

Referring now to FIG. 4G, the process performed by web server 114 inprocessing data packets received from the database query system 112 canbe further explained. In a first step 570, web server 114 receives adata packets from the database query system 112. Step 570 may beperformed in background to other steps in FIG. 4G so that receipt datapackets may continue while data packets are being processed.

When one or more data packets have been received for processing, in step572, the received data packets arc evaluated to select the data packethaving the highest priority level. This highest priority data packet isthen used to generate an alert. The type of alert generated is basedupon the station identifier provided in the data packet. If the datapacket provides an email address (step 574), then in step 576, an emailmessage is generated directed to that email address including a textualmessage describing the alert condition. The message is then sent (step578) and processing returns to step 572. If the station identifier is aTCP/IP address (step 580), then in step 582 web server 114 connects tothis TCP/IP address and delivers a textual alert message in a mannerthat is appropriate to the Internet application in use. Then, in step584, the connection is disconnected and processing returns to step 572.If the data packet selected includes a Internet address for a numericpager service (step 586), then in step 588 a connection is establishedto the pager service and the appropriate numeric code is delivered forthe alert type identified by the data packet. In step 590 the connectionto the page service is disconnected and processing returns to step 572.If a data packet identifies address for an alpha numeric pager server(step 592), then in step 594 a connection is established to the pagerservice and a textual alert is delivered to the pager service. Then instep 596, the connection to the pager service is disconnected and theprocessing returns to step 572.

Referring now to FIG. 4H, the process performed by the switch host 130in, response to data packets received from database query system. 112can be explained in further detail. As described above, data packets canbe received 600 from the database query system 112 in background so thatthe remaining steps of FIG. 4H can be performed as packets arecontinuously received. In a first step 602 the data packets that havebeen received are evaluated to select the data packet having the highestpriority level. After a packet has been selected in step 604, switchhost 130 waits for an idle out dial channel in switch 132. When an idlechannel is available, in step 606 a command is sent to switch 132 to outdial to the station identifier identified in the selected packet.Subsequently, in step 608, the switch will report the call status to theswitch host as the call is performed. If the call is answered (step610), then in step 612 the switch host 130 delivers commands to switch132 to play prerecorded messages corresponding to the alert type of theselected packet and then to hang up the established connection. If thereis no answer or the dialed number is busy (step 614), then the packet ismarked for retry (step 616). After either of step 612 or 616, in step618 a detailed call record is inserted in the subscriber history table194 indicating the results of the call that was placed, i.e., whetherthe call was answered or not answered or busy. Processing then returnsto step 602 to select another data packet for delivery to a subscriber.

Referring now to FIGS. 5A and 5B, the static area process can bedescribed in greater detail. In the static area process, in step 620database query system 112 retrieves all station identifiers ofsubscribers located in the area specified in the alert, which may be astate, county, city, zip code, or other definable region. Then in step622 those station IDs are prioritized based upon the informationregistered for the subscriber. FIG. 5A illustrates exemplary countiesand zip codes that may be utilized in a typical static area process.

Referring now to FIGS. 6A and 6B, the operation of a radius process 536of the database query system 112 can be explained in further detail. Ina radius process, in step 624 all station identifiers for subscriberswithin an identified range of a specific geographic point are retrieved.Then in step 626, the retrieved station identifiers are prioritizedbased upon information registered by the subscribers. As seen in FIG.6A, a radius routine will notify subscribers within one of a number ofpredefined circular regions and mileages 628 surrounding a specificgeographic position, which may be identified by GPS coordinates,latitude and longitude, or even a zip codes or postal address. In thecase of a zip code, which have regions such as are shown in FIG. 6A, thegeographic center of the zip code region will be used as the geographicposition from which to compute the circular region 628.

Referring now to FIGS. 7A and 7B, the operations of a vector process 538performed by database query system 112 can be further explained. As seenin FIG. 7A, in this process the number of geographic locations arecomputed, and from these locations subscribers located within a radiusof those locations are identified for notification of the alertcondition. Each radial region 629 identified during this process isknown as a “band” of geographic locations. The vector process isperformed for a defined number of bands and a defined time frame.

A first step 630 in the vector process is to determine a mileage rangethat can be covered by the hazard (e.g., tornado) in the identified timeframe based upon the identified forward speed. Then in step 632, allstation identifiers for subscribers that are within the calculated rangeof the identified geographic point are retrieved. In step 634 and step636, variables are initialized for later use in collecting additionalstation identifiers. Specifically in step 634, a current geographicpoint is set to be the identified geographic point in the alertnotification packet. In step 636, the band number is initialized to avalue of one.

In a subsequent loop of steps 638, 640, 642, 644 and 646, geographicregions are calculated, and then station IDs for subscribers withinthose geographic regions are identified. In a first step 638, thegeographic region is calculated based upon the current band number andcurrent geographic point. This involves steps similar to those describedabove with reference to steps 630 and 632 in which a mileage range iscomputed and then station IDs for subscribers within that mileage rangeof the current geographic point are identified. After 638, in step 640all station identifiers that are not previously enqueued, that arewithin the geographic region identified in step 638 are enqueued. Instep 642, the current band number is incremented. And in step 644, it isdetermined whether there are additional bands to be included in thevector routine. If so, then in step 646 a new current geographic pointis computed based upon the existing geographic point and the heading,time frame and identified number of bands provided in the alertnotification. This causes the center of subsequent regions to move alongthe heading identified by the alert notification. After step 646,processing returns to step 638 to calculate a new geographic region andqueue additional station identifiers.

After all bands have been completed, the processing proceeds from step644 to step 648 in which the band number again is initialized to a valueof one. Next, in step 650 station IDs identified in the current bandnumber are prioritized based upon subscriber registered information.Thereafter, in step 652 it is determined whether there are more bands,and if so then in step 654 the band number is incremented. After allbands have been processed then the vector process is completed. Thesefinal steps 650, 652 and 654 cause station identifiers to be prioritizedsuch that those in the first band, which are nearest to the hazard orthreat, are prioritized before those in subsequent bands.

Referring now to FIGS. 8A and 8B, the shoreline process 540 of thedatabase query system 112 can be explored. In a first step 660, allstation identifiers within a given coastal area are retrieved. Then instep 662, those station identifiers are prioritized based upon floodzone coding of the corresponding subscriber records. Then in step 664,station identifiers are further prioritizes based upon subscriberregistered information. As seen in FIG. 8A, this process permits alertnotifications to be delivered to multiple subscribers who are threatenedby a coastal hazard such as a tidal wave, high seas or hurricane.

Referring now to FIGS. 9A and 9B, the river routine 542 of the databasequery system 112 can be elaborated. In the first step 670, all stationidentifiers within given riverbank area are retrieved. Then in step 672,those station identifiers are prioritize based upon flood zone code inthe subscriber information. Subsequently, in step 674 those stationidentifiers are again prioritized based upon other registeredinformation from subscribers. As seen in FIG. 9A, this process permitsall subscribers within a flood plane or threatened by flooding in ariver area to be advised of an emergency condition.

Referring now to FIGS. 10A and 10B, details of the wind dispersionprocess 544 of the database query system 112 can be elaborated. In thisprocess, in the first step 680 a mileage range is computed, representingthe range that a toxic release will cover in the identified time framebased upon the identified wind speed. Next, in step 682, all stationidentifiers for subscribers within the calculated range of theidentified geographic point are retrieved. In step 684 and step 686,variables are initialized for a loop of steps 688, 690, 692, 694 and 696in which station identifiers are selected from those retrieved in step682. In step 684, a current geographic point is initialized to be thegeographic point identified in the alert notification packet. In step686, a band number is initialized to a value of one. Subsequently instep 688, a geographic region is calculated based upon the current bandnumber and the current geographic point. This calculation involves winddispersion formulas known in the art which identify areas in which arelease at a given point will be dispersed, given a current winddirection and speed. Subsequently, in step 690, all station identifiersthat have not been previously enqueued and that are within theidentified geographic region are enqueued. Thereafter, in step 692 thecurrent band number is incremented and step 694 it is determined whethermore bands are to be processed. If there are more bands to process, instep 696 a new current geographic point is computed from the previousgeographic point the identified wind speed, time frame and number ofbands identified in the alert notification packet. Processing thenreturns to step 688 to complete another band.

After all bands have been processed, in step 698 the band number isagain initialized to a value one to permit prioritization through step700, 702 and 704. In step 700, all station identifiers for current bandnumber are prioritized based upon subscriber registered information. Instep 702, it is determined whether there are additional bands. If so, instep 704 the current band number is incremented and processing returnsto step 700 to prioritize station IDs for the new current band number.After all bands have been prioritized in this manner, processing iscomplete. These last three steps, 700, 702 and 704 permit all stationidentifiers to be prioritized such that station identifiers identifiedin a given band nearer to the source of the toxic release, areprioritized first and prior to station identifiers identified inadditional bands.

Referring now to FIG. 11, details of the school or organization process546 of the database query system 112 can be explained. In a first step710, the school or organization identifier of the alert notification isused to locate station identifiers for all subscribers that haveregistered a matching school or organization identifier. In a secondstep 712, the retrieved station identifiers are prioritized based uponthe subscribers' registered information and enqueued.

While the present invention has been illustrated by a description ofvarious embodiments and while these embodiments have been described inconsiderable detail, it is not the intention of the applicants torestrict or in any way limit the scope of the appended claims to suchdetail. Additional advantages and modifications will readily appear tothose skilled in the art.

For example, the location information found in the subscriberinformation tables of FIG. 3C need not be static. Several organizationshave recently proposed technologies for tracking the movement ofcommunication equipment such as cellular telephones. Technologies ofthis kind are described in U.S. Pat. Nos. 5,945,944, 5,663,734,5,781,156, 5,825,327, 5,831,574, 5,841,396, 5,812,087, 5,874,914 and5,884,214, all of which are hereby incorporated herein by reference intheir entirety.

Consistent with principles of the present invention, theabove-referenced technology may be utilized to dynamically updatelocation information found in the subscriber information tables of FIG.3C, to reflect the current position of a subscriber's cellular phone orother wireless communication device. Then if the subscriber'scommunication device is within a threatened area that has beenidentified in the manner described above, the subscriber will receive analert notification in the manner described above.

Mobile wireless devices that can be tracked for the purposes ofproviding alert notifications, are not limited to cellular telephones,but could also include personal digital assistant (PDA) devices, orlaptop or palmtop computers having wireless communications capabilities.Furthermore, alerts may be delivered to the mobile wireless device viatechnologies other than voice telephone, such as via paging services(voice or text), or via Internet or e-mail communications as notedabove.

The invention in its broader aspects is therefore not limited to thespecific details, representative apparatus and method, and illustrativeexample shown and described. Accordingly, departures may be made fromsuch details without departing from the spirit or scope of applicant'sgeneral inventive concept.

What is claimed is:
 1. A system for providing a warning signal to aplurality of persons and/or locations on a geographic basis, comprising:a database and a tandem database each storing a plurality ofcommunications identifiers, and storing an association of each saididentifier with a geographic location thereof, a computer system and atandem computer system each responding to a command identifying ageographic area and a warning to be provided to said geographic area, bycomparing geographic locations of communications identifiers with saidgeographic area, retrieving individual matching communicationsidentifiers and establishing a communications connection in response tothe command using each retrieved communications identifier anddelivering said warning via said communications connection, the tandemdatabase and tandem computer system in communication with the databaseand computer system and sharing information regarding warnings to beprovided by either of them, wherein said comparing and retrieving stepsare performed after receipt of said command.
 2. The system of claim 1wherein said system is located in a geographic location distant from atleast some of the geographic locations identified within said database.3. The system of claim 1 wherein said computer system comprises a hostcomputer and a telecommunication interface for receiving telephonenumbers and audio messages from said host computer for delivery to saidtelephone numbers.
 4. The system of claim 1 wherein said communicationsidentifiers are identifiers for use with a publicly switched telephoniccommunications system.
 5. The system of claim 4 wherein saidcommunications identifiers are telephone numbers.
 6. The system of claim5 wherein said telephone numbers comprise an area code, exchange numberand directory number.
 7. The system of claim 6 wherein said telephonenumbers further comprise a country code.
 8. The system of claim 1wherein said communications identifiers are electronic mail addressesfor use with a computer network.
 9. The system of claim 8 wherein saidcomputer network is a global computer network.
 10. The system of claim 9wherein said computer network is the Internet.
 11. The system of claim 1wherein said communications identifiers are Internet protocol addressesfor use with an Internet protocol computer network.
 12. The system ofclaim 11 wherein said computer network is the Internet.
 13. The systemof claim 1 wherein said computer system further comprises a threatidentification system for receiving threat information, said threatidentification system evaluating said threat information to identify ageographic area subject to a threat and in response generate saidcommand identifying said geographic area and a warning related to theidentified threat.
 14. The system of claim 13 wherein said threatidentification system identifies weather threats applicable to saidgeographic area.
 15. The system of claim 14 wherein said threatidentification system comprises a communications connection to aNational Weather Service information service.
 16. The system of claim 15wherein said threat identification system receives text informationdescribing weather conditions and comprises a parser for parsing saidtext information to identify weather threats and geographic areas towhich said threats apply.
 17. The system of claim 1 wherein said warningsignal identifies a weather threat applicable to said geographic area.18. The system of claim 1 wherein said warning signal warns of hazardousatmospheric conditions applicable to said geographic area.
 19. Thesystem of claim 18 wherein said warning signal warns of poor air qualityin said geographic area.
 20. The system of claim 18 wherein said warningsignal warns of a toxic release in said geographic area.
 21. The systemof claim 18 wherein said warning signal warns of harmful radiation insaid geographic area.
 22. A system for providing an atmosphericcondition announcement to a plurality of persons and/or locations,comprising: a database and a tandem database each storing a plurality ofcommunications identifiers for persons and/or locations in need ofatmospheric condition information, and storing an association of eachsaid identifier with identifications of atmospheric conditioninformation to be provided to those persons and/or locations, a computersystem and a tandem computer system each responding to a commandidentifying an atmospheric condition to be announced to said personsand/or locations, by analyzing identifications of atmospheric conditionsin said database to identify target persons and/or locations to benotified of said atmospheric condition, retrieving from said database,individual matching communications identifiers associated with saidtarget persons and/or locations, and establishing a communicationsconnection using each retrieved communications identifier and deliveringan announcement of said atmospheric condition via said communicationsconnection, the tandem database and tandem computer system incommunication with the database and computer system and sharinginformation regarding announcements to be provided by either of them,wherein said analyzing and retrieving steps are performed after receiptof said command.
 23. The system of claim 22 wherein said system islocated in a geographic location distant from at least some of thepersons and/or locations identified within said database.
 24. The systemof claim 22 wherein said computer system comprises a host computer and atelecommunication interface for receiving telephone numbers and audiomessages from said host computer for delivery to said persons and/orlocations.
 25. The system of claim 22 wherein said communicationsidentifiers are identifiers for use with a publicly switched telephoniccommunications system.
 26. The system of claim 25 wherein saidcommunications identifiers are telephone numbers.
 27. The system ofclaim 26 wherein said telephone numbers comprise an area code, exchangenumber and directory number.
 28. The system of claim 27 wherein saidtelephone numbers further comprise a country code.
 29. The system ofclaim 22 wherein said communications identifiers are electronic mailaddresses for use with a computer network.
 30. The system of claim 29wherein said computer network is a global computer network.
 31. Thesystem of claim 30 wherein said computer network is the Internet. 32.The system of claim 22 wherein said communications identifiers areInternet protocol addresses for use with an Internet protocol computernetwork.
 33. The system of claim 32 wherein said computer network is theInternet.
 34. The system of claim 22 wherein said computer systemfurther comprises an atmospheric event identification system forreceiving atmospheric event information, said atmospheric eventidentification system evaluating said atmospheric event information toidentify persons and/or locations interested in an atmospheric event andin response generate said command identifying said announcement relatedto the identified event.
 35. The system of claim 34 wherein saidatmospheric event identification system identifies weather threats. 36.The system of claim 35 wherein said atmospheric event identificationsystem comprises a communications connection to a National WeatherService information service.
 37. The system of claim 36 wherein saidatmospheric event identification system receives text informationdescribing weather conditions and comprises a parser for parsing saidtext information to identify weather events.
 38. The system of claim 22wherein said atmospheric condition announcement identifies a weatherevent applicable to persons and/or locations receiving the message. 39.The system of claim 22 wherein said atmospheric condition announcementwarns of hazardous atmospheric conditions applicable to said geographicarea.
 40. The system of claim 39 wherein said atmospheric conditionannouncement warns of poor air quality in said geographic area.
 41. Thesystem of claim 39 wherein said atmospheric condition announcement warnsof a toxic release in said geographic area.
 42. The system of claim 39wherein said atmospheric condition announcement warns of harmfulradiation in said geographic area.
 43. A system for providingtime-sensitive announcements to a plurality of persons and/or locations,comprising: a database and a tandem database each storing a plurality ofcommunications identifiers, and storing an association of eachcommunications identifier with data useful for determining whetherparticular time-sensitive information is to be communicated to saidcommunications identifier, a computer system and a tandem computersystem each responding to a command identifying an announcement to beannounced to interested persons and/or locations, by comparing saidcommand to said data useful for determining whether particulartime-sensitive information is to be communicated to said persons and/orlocations, retrieving from said database, individual matchingcommunications identifiers associated with persons and/or locations towhom said time-sensitive announcement is to be communicated in responseto the command, and establishing a communications connection using eachretrieved communications identifier and delivering said time-sensitiveannouncement via said communications connection, the tandem database andtandem computer system in communication with the database and computersystem and sharing information regarding announcements to be provided byeither of them, wherein said comparing and retrieving steps areperformed after receipt of said command.
 44. The system of claim 43wherein said system is located in a geographic location distant from atleast some of the persons and/or locations reached by the communicationsidentifiers identified within said database.
 45. The system of claim 43wherein said computer system comprises a host computer and atelecommunication interface for receiving telephone numbers and audiomessages from said host computer for delivery to said telephone numbers.46. The system of claim 43 wherein said communications identifiers areidentifiers for use with a publicly switched telephonic communicationssystem.
 47. The system of claim 46 wherein said communicationsidentifiers are telephone numbers.
 48. The system of claim 47 whereinsaid telephone numbers comprise an area code, exchange number anddirectory number.
 49. The system of claim 48 wherein said telephonenumbers further comprise a country code.
 50. The system of claim 43wherein said communications identifiers are electronic mail addressesfor use with a computer network.
 51. The system of claim 50 wherein saidcomputer network is a global computer network.
 52. The system of claim51 wherein said computer network is the Internet.
 53. The system ofclaim 43 wherein said communications identifiers are Internet protocoladdresses for use with an Internet protocol computer network.
 54. Thesystem of claim 53 wherein said computer network is the Internet. 55.The system of claim 43 wherein said computer system further comprises anevent identification system for receiving event information, said eventidentification system evaluating said event information to identifycommunications identifiers for persons and/or locations interested in anevent and in response generate said command identifying saidannouncement related to the identified event.
 56. The system of claim 55wherein said event identification system identifies weather threats. 57.The system of claim 56 wherein said event identification systemcomprises a communications connection to a National Weather Serviceinformation service.
 58. The system of claim 57 wherein said eventidentification system receives text information describing weatherconditions and comprises a parser for parsing said text information toidentify weather threats.
 59. The system of claim 43 wherein saidannouncement identifies a weather threat applicable to persons and/orlocations receiving the message.
 60. The system of claim 43 wherein saidannouncement warns of hazardous atmospheric conditions applicable to ageographic area.
 61. The system of claim 60 wherein said announcementwarns of poor air quality in said geographic area.
 62. The system ofclaim 60 wherein said announcement warns of a toxic release in saidgeographic area.
 63. The system of claim 60 wherein said announcementwarns of harmful radiation in said geographic area.
 64. The system ofclaim 43 wherein said announcement identifies unavailability of a publicservice at a particular time.
 65. The system of claim 64 wherein saidannouncement identifies a school closing.
 66. The system of claim 43wherein said announcement identifies a traffic condition.
 67. The systemof claim 43 wherein said announcement identifies an unscheduled closingof a public place.
 68. The system of claim 43 wherein said announcementidentifies a change in a regularly scheduled activity.
 69. The system ofclaim 68 wherein said regularly scheduled activity is the movements of apublic transportation system.
 70. The system of claim 68 wherein saidregularly scheduled activity is the hours of business of a place ofpublic accommodation.
 71. The system of claim 1 wherein said computersystem further establishes a prioritization of communicationsidentifiers using data in said database, and establishes saidcommunications connections in a prioritized order.
 72. The system ofclaim 71 wherein data in said database includes characteristics of aperson and/or location addressed by a communications identifier, andprioritization of communications identifiers includes determiningpersons and/or locations most likely to be adversely affected by thesubject matter of said warning.
 73. The system of claim 72 wherein saiddata in said database enables distinction of buildings at locationsaddressed by communications identifiers.
 74. The system of claim 73wherein said data in said database enables distinction of the heights ofbuildings at locations addressed by communications identifiers.
 75. Thesystem of claim 73 wherein said data in said database enablesdistinction of temporary and permanent buildings at locations addressedby communications identifiers.
 76. The system of claim 72 wherein saiddata in said database enables distinction of locations susceptible toflooding that are addressed by communications identifiers.
 77. Thesystem of claim 71 wherein said data in said database includescharacteristics of persons and/or locations addressed by communicationsidentifiers, and prioritization of communications identifiers includesdetermining persons most likely to be adversely affected by the subjectmatter of said warning.
 78. The system of claim 77 wherein said data insaid database enables distinction of persons requiring specialassistance to seek shelter that are addressed by communicationsidentifiers.
 79. The system of claim 77 wherein said data in saiddatabase enables distinction of persons particularly susceptible torespiratory distress that are addressed by communications identifiers.80. The system of claim 22 wherein said computer system furtherestablishes a prioritization of communications identifiers using data insaid database, and establishes said communications connections in aprioritized order.
 81. The system of claim 80 wherein data in saiddatabase includes characteristics of a person and/or location addressedby a communications identifier, and prioritization of communicationsidentifiers includes determining persons and/or locations most likely tobe adversely affected by the atmospheric condition that is the subjectof said announcement.
 82. The system of claim 81 wherein said data insaid database enables distinction of buildings at locations addressed bycommunications identifiers.
 83. The system of claim 82 wherein said datain said database enables distinction of the heights of buildings atlocations addressed by communications identifiers.
 84. The system ofclaim 82 wherein said data in said database enables distinction oftemporary and permanent buildings at locations addressed bycommunications identifiers.
 85. The system of claim al wherein said datain said database enables distinction of locations susceptible toflooding that are addressed by communications identifiers.
 86. Thesystem of claim 80 wherein said data in said database includescharacteristics of persons and/or locations addressed by communicationsidentifiers, and prioritization of communications identifiers includesdetermining persons and/or locations most likely to be adverselyaffected by the atmospheric condition that is the subject of saidannouncement.
 87. The system of claim 86 wherein said data in saiddatabase enables distinction of persons requiring special assistance toseek shelter that are addressed by communications identifiers.
 88. Thesystem of claim 86 wherein said data in said database enablesdistinction of persons particularly susceptible to respiratory distressthat are addressed by communications identifiers.
 89. The system ofclaim 43 wherein said computer system further establishes aprioritization of communications identifiers using data in saiddatabase, and establishes said communications connections in aprioritized order.
 90. The system of claim 89 wherein data in saiddatabase includes characteristics of a person and/or location addressedby a communications identifier, and prioritization of communicationsidentifiers includes determining persons and/or locations most likely tobe adversely affected by the subject matter of said announcement. 91.The system of claim 90 wherein said data in said database enablesdistinction of buildings at locations addressed by communicationsidentifiers.
 92. The system of claim 91 wherein said data in saiddatabase enables distinction of the heights of buildings at locationsaddressed by communications identifiers.
 93. The system of claim 91wherein said data in said database enables distinction of temporary andpermanent buildings at locations addressed by communicationsidentifiers.
 94. The system of claim 90 wherein said data in saiddatabase enables distinction of locations susceptible to flooding thatare addressed by communications identifiers.
 95. The system of claim 89wherein said data in said database includes characteristics of personsand/or locations addressed by communications identifiers, andprioritization of communications identifiers includes determiningpersons most likely to be adversely affected by the subject matter ofsaid announcement.
 96. The system of claim 95 wherein said data in saiddatabase enables distinction of persons requiring special assistance toseek shelter that are addressed by communications identifiers.
 97. Thesystem of claim 95 wherein said data in said database enablesdistinction of persons particularly susceptible to respiratory distressthat are addressed by communications identifiers.
 98. The system ofclaim 1 wherein said database stores first and second communicationsidentifiers associated with separately identified geographic locationswithin a given geographic area.
 99. The system of claim 98 wherein saidsystem responds to a command identifying said given geographic area byretrieving said first and second communications identifiers.
 100. Thesystem of claim 1 wherein said database stores, for each of a pluralityof warning types, data relevant to each said warning type.
 101. Thesystem of claim 100 wherein said database stores association ofcommunications identifiers with warning types, said command identifies awarning type, and said computer system compares warning types ofcommunications identifiers with a warning type of a command anddetermines whether there is a match.
 102. The system of claim 100wherein said database stores an indication of system users authorized togenerate a warning type, said command identifies a warning type, andsaid system determines whether a user originating a command isauthorized to generate a warning of the type identified by a command aspart of responding to the command.
 103. The system of claim 13 whereinsaid threat identification system projects a path expected to befollowed by a threat and identifies a geographic area subject to saidthreat based on the projected path.
 104. The system of claim 103 whereinsaid threat identification system is responsive to said path and statusinformation on previously executed commands to discontinue issuance ofwarnings based on said command.
 105. The system of claim 103 whereinsaid threat identification system is responsive to said path and statusinformation on previously executed commands to identify communicationsidentifiers not identified from previously executed commands.
 106. Thesystem of claim 13 wherein said threat identification system evaluatesone or more of a location of a threat a speed of a threat a heading of athreat a shape of a threat to identify a geographic area subject to athreat.
 107. The system of claim 14 wherein said threat identificationsystem comprises a communications connection to a weather radar system.108. The system of claim 8 wherein said electronic mail addressescorrespond to text pagers.
 109. The system of claim 1 wherein saidcomputer system is further responsive to identifying a location of amobile device addressed by a communications identifier, by storing insaid database an association of said communications identifier with saidlocation.
 110. The system of claim 109 wherein said computer systemestablishes a communications connection and delivers a warning to amobile device which has been identified in tracking information to be ata location which matches a geographic area identified in a command thatidentifies said warning.
 111. The system of claim 71 wherein saidprioritization is based upon the proximity of a threat to the geographiclocations associated with said communications identifiers.
 112. Thesystem of claim 71 wherein said computer system establishes aprioritization using a criterion for public switched telecommunicationsnetwork resources.
 113. The system of claim 71 wherein saidprioritization provides enhanced priority to communications identifiersof persons and/or locations that will or may provide said warning toother persons and/or locations.
 114. The system of claim 73 wherein saidcomputer system prioritizes buildings based upon adequacy of shelterprovided by said buildings.
 115. The system of claim 73 wherein saidcomputer system prioritizes more populous buildings before less populousbuildings.
 116. The system of claim 73 wherein said computer systemprioritizes buildings based upon their purposes.
 117. The system ofclaim 116 wherein said computer system prioritizes buildings that caterto one or more of elderly, juvenile, infirm or ill persons beforebuildings catering to the general public.
 118. The system of claim 78wherein said data in said database enables distinction of personsrequiring special assistance due based on one or more of an elderly,juvenile, infirm or ill condition of such persons.
 119. The system ofclaim 22 wherein said database stores first and second communicationsidentifiers associated with separately identified atmosphericconditions.
 120. The system of claim 119 wherein said system responds toa command identifying an atmospheric condition matching the atmosphericconditions associated with said first and second communicationsidentifiers by retrieving said first and second communicationsidentifiers.
 121. The system of claim 22 wherein said database stores,for each of a plurality of atmospheric condition types, data relevant toeach said atmospheric condition type.
 122. The system of claim 121wherein said database stores association of communications identifierswith atmospheric condition types, said command identifies an atmosphericcondition type, and said computer system compares atmospheric conditiontypes of communications identifiers with an atmospheric condition typeof a command and determines whether there is a match.
 123. The system ofclaim 121 wherein said database stores an indication of system usersauthorized to annoyances an atmospheric condition, said commandidentifies an atmospheric condition, and said system determines whethera user originating a command is authorized to announce atmosphericcondition identified by a command as part of responding to the command.124. The system of claim 34 wherein said atmospheric eventidentification system projects a path expected to be followed by anatmospheric condition and identifies persons and/or locations subject tosaid atmospheric condition based on the projected path.
 125. The systemof claim 124 wherein said event identification system is responsive tosaid path and status information on previously executed commands todiscontinue issuance of announcements based on previously identifiedcommands.
 126. The system of claim 124 wherein said event identificationsystem is responsive to said path and status information on previouslyexecuted commands to identify communications identifiers not identifiedfrom previously executed commands.
 127. The system of claim 34 whereinsaid atmospheric event identification system evaluates one or more of alocation of an atmospheric condition a speed of an atmospheric conditiona heading of an atmospheric condition a shape of an atmosphericcondition to identify persons and/or locations subject to an atmosphericcondition.
 128. The system of claim 35 wherein said threat eventidentification system comprises a communications connection to a weatherradar system.
 129. The system of claim 29 wherein said electronic mailaddresses correspond to text pagers.
 130. The system of claim 22 whereinsaid computer system is further responsive to identifying a location ofa mobile device addressed by a communications identifier, by storing insaid database an association of said communications identifier with saidlocation.
 131. The system of claim 130 wherein said computer systemestablishes a communications connection and delivers an announcement toa mobile device which has been identified in tracking information to beat a location which matches a geographic area identified in a commandthat identifies said announcement.
 132. The system of claim so whereinsaid announcement relates to an atmospheric threat, and saidprioritization is based upon the proximity of the threat to thegeographic locations associated with said communications identifiers.133. The system of claim 80 wherein said computer system establishes aprioritization using a criterion for public switched telecommunicationsnetwork resources.
 134. The system of claim 80 wherein saidprioritization provides enhanced priority to communications identifiersof persons and/or locations that will or may provide said announcementto other persons and/or locations.
 135. The system of claim 82 whereinsaid computer system prioritizes buildings based upon adequacy ofshelter provided by said buildings.
 136. The system of claim 82 whereinsaid computer system prioritizes more populous buildings before lesspopulous buildings.
 137. The system of claim 82 wherein said computersystem prioritizes buildings based upon their purposes.
 138. The systemof claim 137 wherein said computer system prioritizes buildings thatcater to one or more of elderly, juvenile, infirm or ill persons beforebuildings catering to the general public.
 139. The system of claim 87wherein said data in said database enables distinction of personsrequiring special assistance due based on one or more of an elderly,juvenile, infirm or ill condition of such persons.
 140. The system ofclaim 43 wherein said database stores first and second communicationsidentifiers associated with separately identified data useful fordetermining whether particular information is to be communicated to saidcommunications identifiers.
 141. The system of claim 140 wherein saidsystem responds to a command identifying an announcement matching saiddata useful for determining whether particular information is to becommunicated to said communications identifiers by retrieving said firstand second communications identifiers.
 142. The system of claim 43wherein said database stores, for each of a plurality of announcementtypes, data relevant to each said announcement type.
 143. The system ofclaim 142 wherein said database stores association of communicationsidentifiers with announcement types, said command identifies anannouncement type, and said computer system compares announcement typesof communications identifiers with an announcement type of a command anddetermines whether there is a match.
 144. The system of claim 142wherein said database stores an indication of system users authorized togenerate an announcement type, said command identifies an announcementtype, and said system determines whether a user originating a command isauthorized to generate an announcement of the type identified by acommand as part of responding to the command.
 145. The system of claim55 wherein said event identification system projects a path expected tobe followed by an atmospheric condition and identifies a geographic areasubject to said atmospheric condition based on the projected path. 146.The system of claim 145 wherein said event identification system isresponsive to said path and status information on previously executedcommands to discontinue issuance of announcements based on previouslyidentified commands.
 147. The system of claim 124 wherein said eventidentification system is responsive to said path and status informationon previously executed commands to identify communications identifiersnot identified from previously executed commands.
 148. The system ofclaim 55 wherein said event identification system evaluates one or moreof a location of an event condition a speed of an event condition aheading of an event condition a shape of an event condition to identifya geographic area subject to an event condition.
 149. The system ofclaim 56 wherein said event identification system comprises acommunications connection to a weather radar system.
 150. The system ofclaim 50 wherein said electronic mail addresses correspond to textpagers.
 151. The system of claim 43 wherein said computer system isfurther responsive to identifying a location of a mobile deviceaddressed by a communications identifier, by storing in said database anassociation of said communications identifier with said location. 152.The system of claim 151 wherein said computer system establishes acommunications connection and delivers an announcement to a mobiledevice which has been identified in tracking information to be at alocation which matches a geographic area identified in a command thatidentifies said announcement.
 153. The system of claim 89 wherein saidannouncement relates to an atmospheric threat, and said prioritizationis based upon the proximity of the threat to the geographic locationsassociated with said communications identifiers.
 154. The system ofclaim 89 wherein said computer system establishes a prioritization usinga criterion for public switched telecommunications network resources.155. The system of claim 89 wherein said prioritization providesenhanced priority to communications identifiers of persons and/orlocations that will or may provide said announcement to other personsand/or locations.
 156. The system of claim 91 wherein said computersystem prioritizes buildings based upon adequacy of shelter provided bysaid buildings.
 157. The system of claim 91 wherein said computer systemprioritizes more populous buildings before less populous buildings. 158.The system of claim 91 wherein said computer system prioritizesbuildings based upon their purposes.
 159. The system of claim 158wherein said computer system prioritizes buildings that cater to one ormore of elderly, juvenile, infirm or ill persons before buildingscatering to the general public.
 160. The system of claim 96 wherein saiddata in said database enables distinction of persons requiring specialassistance due based on one or more of an elderly, juvenile, infirm orill condition of such persons.
 161. The system of claim 1 wherein saidtandem computer system and tandem database are located in a geographiclocation distant from said computer system and database.
 162. The systemof claim 1 wherein said tandem computer system and tandem database arelocated in a common geographic location with said computer system anddatabase.
 163. The system of claim 1 wherein said computer systemscommunicate to task one of them with handling each warning delivery.164. The system of claim 1 wherein, in the event of a failure of one ofsaid databases or computer systems, the other database or computersystem handles all outstanding warning deliveries.
 165. The system ofclaim 1 wherein said computer systems communicate to synchronize data insaid databases.
 166. The system of claim 165 wherein said computersystem tasks said tandem computer system to concurrently deliverwarnings with said computer system.
 167. The system of claim 165 whereinsaid computer system delivers to said tandem computer system one or moreof a command, identifier selection criteria for a command, a warning,prioritization information regarding communications identifiers, andcommunications identifiers.
 168. The system of claim 165 wherein saidcomputer systems exchange status and recipient response informationregarding the delivery of warnings.
 169. The system of claim 22 whereinsaid tandem computer system and tandem database are located in ageographic location distant from said computer system and database. 170.The system of claim 22 wherein said tandem computer system and tandemdatabase are located in a common geographic location with said computersystem and database.
 171. The system of claim 22 wherein said computersystems communicate to task one of them with handling each announcementdelivery.
 172. The system of claim 22 wherein, in the event of a failureof one of said databases or computer systems, the other database orcomputer system handles all outstanding announcement deliveries. 173.The system of claim 22 wherein said computer systems communicate tosynchronize data in said databases.
 174. The system of claim 173 whereinsaid computer system tasks said tandem computer system to concurrentlydeliver announcements with said computer system.
 175. The system ofclaim 173 wherein said computer system delivers to said tandem computersystem one or more of a command, identifier selection criteria for acommand, an announcement, prioritization information regardingcommunications identifiers, and communications identifiers.
 176. Thesystem of claim 173 wherein said computer systems exchange status andrecipient response information regarding the delivery of announcements.177. The system of claim 43 wherein said tandem computer system andtandem database is located in a geographic location distant from saidcomputer system and database.
 178. The system of claim 43 wherein saidtandem computer system and tandem database are located in a commongeographic location with said computer system and database.
 179. Thesystem of claim 43 wherein said computer systems communicate to task oneof them with handling each announcement delivery.
 180. The system ofclaim 43 wherein, in the event of a failure of one of said databases orcomputer systems, the other database or computer system handles alloutstanding announcement deliveries.
 181. The system of claim 43 whereinsaid computer systems communicate to synchronize data in said databases.182. The system of claim 181 wherein said computer system tasks saidtandem computer system to concurrently deliver announcements with saidcomputer system.
 183. The system of claim 181 wherein said computersystem delivers to said tandem computer system one or more of a command,identifier selection criteria for a command, an announcement,prioritization information regarding communications identifiers, andcommunications identifiers.
 184. The system of claim 181 wherein saidcomputer systems exchange status and recipient response informationregarding the delivery of announcements.
 185. The system of claim 3wherein said telecommunication interface comprises a host controlledtelephone switch coupled to said host computer.
 186. The system of claim24 wherein said telecommunication interface comprises a host controlledtelephone switch coupled to said host computer.
 187. The system of claim45 wherein said telecommunication interface comprises a host controlledtelephone switch coupled to said host computer.
 188. The system of claim1 wherein said communications identifiers are telephone numbers, andsaid association is an association of one or more of an area code orexchange of said telephone numbers with geographic locations.
 189. Thesystem of claim 1 wherein said computer system is responsive to statusinformation on previously executed commands in determining a manner ofresponding to a command.
 190. The system of claim 189 wherein saidcomputer system is responsive to a command and status information onpreviously executed commands to discontinue issuance of warnings basedon previously executed commands.
 191. The system of claim 189 whereinsaid computer system is responsive to a command and status informationon previously executed commands to identify communications identifiersof persons and/or locations that have not already received a warningbased on previously executed commands.
 192. The system of claim 22wherein said computer system is responsive to status information onpreviously executed commands in determining a manner of responding to acommand.
 193. The system of claim 192 wherein said computer system isresponsive to a command and status information on previously executedcommands to discontinue issuance of announcements based on previouslyexecuted commands.
 194. The system of claim 192 wherein said computersystem is responsive to a command and status information on previouslyexecuted commands to identify communications identifiers of personsand/or locations that have not already received an announcement based onpreviously executed commands.
 195. The system of claim 55 wherein saidevent identification system is responsive to status information onpreviously executed commands in determining-a manner of responding tosaid command.
 196. The system of claim 195 wherein said computer systemis responsive to a command and status information on previously executedcommands to discontinue issuance of announcements based on previouslyexecuted commands.
 197. The system of claim 195 wherein said computersystem is responsive to a command and status information on previouslyexecuted commands to identify communications identifiers of personsand/or locations that have not already received an announcement based onpreviously executed commands.
 198. The system of claim 15 wherein saidcommunications connection is an Internet connection.
 199. The system ofclaim 15 wherein said communications connection is a radio connection.200. The system of claim 15 wherein said communications connection is asatellite connection.
 201. The system of claim 36 wherein saidcommunications connection is an Internet connection.
 202. The system ofclaim 36 wherein said communications connection is a radio connection.203. The system of claim 36 wherein said communications connection is asatellite connection.
 204. The system of claim 57 wherein saidcommunications connection is an Internet connection.
 205. The system ofclaim 57 wherein said communications connection is a radio connection.206. The system of claim 57 wherein said communications connection is asatellite connection.
 207. A method for warning a plurality of personsand/or locations on a geographic basis, comprising: storingsimultaneously at tandem locations a plurality of communicationsidentifiers, and storing an association of each said identifier with ageographic location thereof, responding at one or both of said tandemlocations to a command identifying a geographic area and a warning to beprovided to said geographic area, by comparing geographic locations ofcommunications identifiers with said geographic area, retrievingindividual matching communications identifiers and establishing acommunications connection in response to the command using eachretrieved communications identifier and delivering said warning via saidcommunications connection, communicating and sharing information betweenthe tandem locations regarding warnings to be provided by either ofthem, wherein said comparing and retrieving steps are performed afterreceipt of said command.
 208. The method of claim 207 performed using ahost computer and a telecommunication interface for receiving telephonenumbers and audio messages from said host computer for delivery to saidtelephone numbers.
 209. The method of claim 207 further comprisingidentifying threats by receiving threat information, evaluating saidthreat information to identify a geographic area subject to a threat andin response generating said command identifying said geographic area anda warning related to the identified threat.
 210. The method of claim 207further comprising establishing a prioritization of communicationsidentifiers using data, wherein said communications connections areestablished in a prioritized order.
 211. The method of claim 207 furthercomprising identifying a location of a mobile device addressed by acommunications identifier, and storing an association of saidcommunications identifier with said location.
 212. The method of claim211 wherein a communications connection is established and a warning isdelivered to a mobile device which has been identified in trackinginformation to be at a location which matches a geographic areaidentified in a command that identifies said warning.
 213. A method forproviding an atmospheric condition announcement to a plurality ofpersons and/or locations, comprising: storing simultaneously at tandemlocations a plurality of communications identifiers for persons and/orlocations in need of atmospheric condition information, and storing anassociation of each said identifier with identifications of atmosphericcondition information to be provided to those persons and/or locations,responding at one or both of said tandem locations to a commandidentifying an atmospheric condition to be announced to said personsand/or locations, by analyzing stored identifications of atmosphericconditions to identify target persons and/or locations to be notified ofsaid atmospheric condition, retrieving from said database, individualmatching communications identifiers associated with said target personsand/or locations, and establishing a communications connection usingeach retrieved communications identifier and delivering an announcementof said atmospheric condition via said communications connection,communicating and sharing information between the tandem locationsregarding announcements to be provided by either of them, wherein saidanalyzing and retrieving steps are performed after receipt of saidcommand.
 214. The method of claim 213 performed using a host computerand a telecommunication interface for receiving telephone numbers andaudio messages from said host computer for delivery to said personsand/or locations.
 215. The method of claim 213 further comprisingidentifying atmospheric events by receiving atmospheric eventinformation, evaluating said atmospheric event information to identifypersons and/or locations interested in an atmospheric event, and inresponse generating said command identifying said announcement relatedto the identified event.
 216. The method of claim 213 further comprisingestablishing a prioritization of communications identifiers using storeddata, wherein said communications connections are established in aprioritized order.
 217. The method of claim 213 further comprisingidentifying a location of a mobile device addressed by a communicationsidentifier, and storing an association of said communications identifierwith said location.
 218. The method of claim 217 wherein acommunications connection is established and an announcement isdelivered to a mobile device which has been identified in trackinginformation to be at a location which matches a geographic areaidentified in a command that identifies said announcement.
 219. A methodfor providing time-sensitive announcements to a plurality of personsand/or locations, comprising: storing simultaneously at tandem locationsa plurality of communications identifiers, and storing an association ofeach communications identifier with data useful for determining whetherparticular time-sensitive information is to be communicated to saidcommunications identifier, responding at one or both of said tandemlocations to a command identifying an announcement to be announced tointerested persons and/or locations, by comparing said command to saiddata useful for determining whether particular time-sensitiveinformation is to be-communicated to said persons and/or locations,retrieving individual matching communications identifiers associatedwith persons and/or locations to whom said time-sensitive announcementis to be communicated in response to the command, and establishing acommunications connection using each retrieved communications identifierand delivering said time-sensitive announcement via said communicationsconnection, communicating and sharing information between the tandemlocations regarding announcements to be provided by either of them,wherein said comparing and retrieving steps are performed after receiptof said command.
 220. The method of claim 219 performed utilizing a hostcomputer and a telecommunication interface for receiving telephonenumbers and audio messages from said host computer for delivery to saidtelephone numbers.
 221. The method of claim 219 further comprisingidentifying event by receiving event information, evaluating said eventinformation to identify communications identifiers for persons and/orlocations interested in an event and in response generating said commandidentifying said announcement related to the identified event.
 222. Themethod of claim 219 further comprising establishing a prioritization ofcommunications identifiers using stored data, wherein saidcommunications connections are established in a prioritized order. 223.The method of claim 219 further comprising identifying a location of amobile device addressed by a communications identifier, and storing anassociation of said communications identifier with said location. 224.The method of claim 223 communications connection is established and anannouncement is delivered to a mobile device which has been identifiedin tracking information to be at a location which matches a geographicarea identified in a command that identifies said announcement.
 225. Themethod of claim 207 further comprising responding to status informationon previously executed commands in determining a manner of responding toa command.
 226. The method of claim 213 further comprising responding tostatus information on previously executed commands in determining amanner of responding to a command.
 227. The method of claim 219 furthercomprising responding to status information on previously executedcommands in determining a manner of responding to a command.